home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
tsql
/
doc
/
benchmark.mail
/
000005_rts _Thu Aug 12 16:18:11 1993.msg
< prev
next >
Wrap
Internet Message Format
|
1996-01-31
|
4KB
Received: from boojum.CS.Arizona.EDU by optima.CS.Arizona.EDU (5.65c/15) via SMTP
id AA29418; Thu, 12 Aug 1993 16:18:12 MST
Date: Thu, 12 Aug 1993 16:18:11 MST
From: "Rick Snodgrass" <rts>
Message-Id: <199308122318.AA02309@boojum.cs.arizona.edu>
Received: by boojum.cs.arizona.edu; Thu, 12 Aug 1993 16:18:11 MST
To: tdbbenchmark@cs.arizona.edu
Subject: Re: Benchmark initiative--update and requests
(Page numbers refer to the workshop proceedings version.)
1. New benchmark queries
I have no new queries to propose.
2. Integration of appendices
To address my concerns raised in my appendix of the previous draft,
I propose the following concrete changes.
* Add "From 4/1/87 to the present, he has managed the Book department."
in line 10 of the second column on page 4.
* Replace the last sentence of the first full paragraph on page QQ-6
with "Third, like the first argument, the second argument may be
computed from valid times and/or user-defined attribute values in the
argument tuples."
* Remove the first sentence of the italicized paragraph at the end
of section 6.4.2.
* Replace the two possibilities, Derived and Imposed, for the value of
the valid-time attribute in Figure 6 with four possibilities:
Intersection, Union, Derived, and Imposed. Add Intersection and Union
to the rightmost set of Figure 2. Add the following after the "a
derived value is computer solely..." sentence: "The derived value
may involve the intersection of the underlying valid-time
components, a union of the underlying components, or may be computed
in some other way from the valid-time components (termed, simply,
derived.)" The following queries, with a current vaid-time component
of "Derived," would be reclassified as follows.
Q 3.9.1: Intersection
Q 3.9.2: Value
Q 3.9.3: Intersection
Q 3.9.4: Intersection
Q 3.9.5: Intersection
Q 3.9.6: Intersection
Q 3.9.7: Union
Q 4.1.1: Value
Q 4.1.2: Value
Q 4.1.3: Value
Q 4.1.4: Value
Q 4.1.5: Value
Q 4.2.1: Value
Q 4.2.2: Value
Q 4.2.3: Value
Q 4.2.4: Intersection
Q 4.2.5: Value
Q 4.3.1: Intersection
Q 4.3.2: Derived
Q 4.3.3: Derived
Q 4.3.4: Derived
Q 4.3.5: Intersection
Q 4.3.6: Derived
Q 4.3.7: Derived
Q 4.4.6: Value
Q 4.5.1: None
Q 4.5.2: Value
Q 4.5.3: Value
Q 4.5.4: Intersection
Q 4.5.5: Intersection
Q 4.5.6: Derived
Q 4.6.1: Value
Q 4.6.2: Value
Q 4.6.3: Derived
Q 4.6.4: Value
Q 4.6.5: Value
Q 4.6.6: Value
I'll be happy to reclassify any remaining queries, if Christian
so desires, to complete this change.
3. Revision of queries
With the above changes, the following changes to the queries are
required.
* Change the category of Q 4.2.5 to "(Projected, Interval, Derived) /
(Duration, Interval, Computed) / (=, Constant) (=, Constant)
4. Authorship
I think the presentation of the authors and the appendix is
entirely appropriate.
5. Strawman proposals for revised sections
I feel that Christian did an excellent job in addressing the
concerns raised at the workshop. I have only a few typographical
remarks.
page 1, 2nd column, line 10 "represents as such" replace with "as such
represents"
page 2 replace "!" with "."
1st column, line 2 remove comma after constructed
page 3, 1st column, line -15 replace "name, salary, and department" with
"name and salary"
line -13 replace "n-m" with "$n$-$m$", ditto throughout
somewhere mention that all three relationships are
time varying
2nd column, line 21 Put \noindent before "Note that..."